From 1cd1fa0faf512029d402d81d4be021c7c6a4b787 Mon Sep 17 00:00:00 2001 From: Alex Burka Date: Thu, 21 Apr 2016 13:55:24 -0400 Subject: [PATCH] fix rerun-if-changed documentation The documentation corresponded to the initial proposed implementation, which was changed to remove special handling of directories before it was ever merged. --- src/doc/build-script.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/doc/build-script.md b/src/doc/build-script.md index fa4007479..2839052b1 100644 --- a/src/doc/build-script.md +++ b/src/doc/build-script.md @@ -72,8 +72,12 @@ crate is built: build script should be re-run if it changes (detected by a more-recent last-modified timestamp on the file). Normally build scripts are re-run if any file inside the crate root changes, but this can be used to scope changes - to just a small set of files. If this path points to a directory the entire - directory will be traversed for changes. + to just a small set of files. (If this path points to a directory the entire + directory will not be traversed for changes -- only changes to the timestamp + of the directory itself (which corresponds to some types of changes within the + directory, depending on platform) will trigger a rebuild. To request a re-run + on any changes within an entire directory, print a line for the directory and + another line for everything inside it, recursively.) Any other element is a user-defined metadata that will be passed to dependencies. More information about this can be found in the [`links`][links] -- 2.30.2